Method and apparatus for mutually exclusive access to network slices in wireless communication system

ABSTRACT

A method, performed by a base station (BS), of supporting access to network slices in a wireless communication system includes: receiving a registration request message including requested network slice identification information of a user equipment (UE) and network slice group identification information corresponding to the requested network slice identification information; selecting an access and mobility management function (AMF) to which the registration request message is to be transmitted based on the registration request message and network slice group information and network slice information supported by at least one AMF stored in the BS; transmitting the registration request message to the AMF; receiving a registration accept message in response to the registration request message; and transmitting the registration accept message to the UE.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of application Ser. No. 16/539,864,now U.S. Pat. No. 11,206,610, which is based on and claims priorityunder 35 U.S.C. § 119 to Korean Patent Application No. 10-2018-0094627,filed on Aug. 13, 2018, in the Korean Intellectual Property Office, thedisclosures of which are incorporated by reference herein in theirentirety.

BACKGROUND 1. Field

The disclosure relates to a method of providing network slicing in awireless communication system.

2. Description of Related Art

In order to meet the increasing demand with respect to wireless datatraffic because of the commercialization of 4G communication systems,efforts have been made to develop improved 5G communication systems orpre-5G communication systems. For this reason, 5G communication systemsor pre-5G communication systems are called Beyond 4G networkcommunication systems or Post Long Term Evolution (LTE) systems. Inorder to achieve a high data transfer rate, consideration is given toimplementing 5G communication systems in millimeter wave (mmW) frequencybands (e.g., 60 GHz bands). In order to reduce propagation path loss andincrease a propagation distance in millimeter wave frequency bands, in5G communication systems, discussions are underway about technologiessuch as beamforming, massive multiple-input and multiple-output (MIMO),full dimensional MIMO (FD-MIMO), array antenna, analog beamforming, andlarge scale antenna which are applied to new radio (NR) systems. Also,in order to improve networks of systems, in 5G communication systems,development of technologies such as evolved small cell, advanced smallcell, cloud radio access network (cloud RAN), ultra-dense network,device to device communication (D2D), wireless backhaul, moving network,cooperative communication, coordinated multi-points (CoMP), andinterference cancellation is underway. Furthermore, in 5G communicationsystems, development of an advanced coding modulation (ACM) scheme suchas hybrid FSK and QAM modulation (FQAM) or sliding window superpositioncoding (SWSC) and an enhanced network access scheme such as filter bankmulti-carrier (FBMC), non-orthogonal multiple access (NOMA), or sparsecode multiple access (SCMA) is underway.

The Internet is evolving from a human-centered connection networkthrough which humans create and consume information to an Internet ofThings (IoT) network through which distributed elements such as objectsexchange and process information. Internet of Everything (IoE)technology, which is a combination of IoT technology and big dataprocessing technology through connection with a cloud server, is alsoemerging. In order to implement the IoT, technology elements such assensing technology, wired/wireless communication and networkinfrastructure, service interface technology, and security technologyare required, and thus technology for inter-object connection, such as asensor network, machine to machine (M2M) communication, or machine typecommunication (MTC), has recently been studied. In an IoT environment,intelligent Internet technology (IT) services that collect and analyzedata generated by connected objects and create new value in human lifemay be provided. The IoT may be applied to fields such as smart homes,smart buildings, smart cities, smart cars or connected cars, smartgrids, health care, smart home appliances, and advanced medical servicesthrough convergence and integration of existing information technology(IT) and various industries.

Various attempts have been made to apply 5G communication systems to IoTnetworks. For example, technology such as sensor network, M2Mcommunication, or MTC is implemented by 5G technology such asbeamforming, MIMO, or array antenna. The application of a cloud RAN asbig data processing technology may also be considered as an example ofconvergence of 5G technology and IoT technology.

Because mobile communication systems may provide various services due tothe development of the mobile communication systems, there is demand formethods of effectively providing such services.

SUMMARY

Provided are an apparatus and method for effectively providing servicesin a mobile communication system.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented embodiments of the disclosure

According to an embodiment of the disclosure a method, performed by abase station (BS), of supporting access to network slices in a wirelesscommunication system includes: receiving a registration request messageincluding requested network slice identification information of a userequipment (UE) and network slice group identification informationcorresponding to the requested network slice identification information;selecting an access and mobility management function (AMF) to which theregistration request message is to be transmitted based on theregistration request message and network slice group information andnetwork slice information supported by at least one AMF stored in theBS; transmitting the registration request message to the AMF; receivinga registration accept message in response to the registration requestmessage; and transmitting the registration accept message to the UE.

The method may further include: transmitting a connection setup requestmessage including network slice identification information supported bythe BS to the at least one AMF; receiving a connection setup responsemessage including network slice information supported by each AMF andnetwork slice group information associated with a network slice group towhich each AMF belongs, in response to the connection setup requestmessage; storing network slice identification information supported byeach AMF and slice group identification information associated with thenetwork slice group to which each AMF belongs; and providing networkslice-related information to the UE based on the stored information.

The network slice-related information may include at least one of thenetwork slice identification information supported by each AMF, thenetwork slice group identification information associated with thenetwork slice group to which each AMF belongs, or network identificationinformation supported by the BS.

The providing of the network slice-related information to the UE mayinclude broadcasting system information including the networkslice-related information.

The registration accept message may include network slice configurationinformation including updated network slice identification informationand network slice group identification information corresponding to theupdated network slice identification information.

The method may further include transmitting, to the UE, a configurationinformation updating request message including network sliceconfiguration information including updated network slice identificationinformation and network slice group identification informationcorresponding to the updated network slice identification information.

The requested network slice identification information may include anidentifier of at least one network slice, and the at least one networkslice may be included in the same network slice group.

According to another embodiment of the disclosure, a method, performedby a user equipment (UE), of supporting access to network slices in awireless communication system includes: generating a registrationrequest message including requested network slice identificationinformation and network slice group identification informationcorresponding to the requested network slice identification information,based on stored network slice configuration information; transmittingthe generated registration request message to a base station (BS);receiving a registration accept message in response to the registrationrequest message; and transmitting the registration accept message to theBS.

The requested network slice identification information may include anidentifier of at least one network slice, and the at last one networkslice may be included in the same network slice group as a network slicegroup associated with the network slice group identificationinformation.

The registration accept message may include network slice configurationinformation including updated network slice identification informationand network slice group identification information corresponding to theupdated network slice identification information.

According to another embodiment of the disclosure, a base station (BS)for supporting access to network slices includes: a transceiver; and acontroller coupled to the transceiver and configured to receive aregistration request message including requested network sliceidentification information of a user equipment (UE) and network slicegroup identification information corresponding to the requested networkslice identification information, select an access and mobilitymanagement function (AMF) to which the registration request message isto be transmitted based on the registration request message and networkslice group information and network slice information supported by atleast one AMF stored in the BS, transmit the registration requestmessage to the AMF, receive a registration accept message in response tothe registration request message, and transmit the registration acceptmessage to the UE.

The controller may be further configured to transmit a connection setuprequest message including network slice identification informationsupported by the BS to the at least one AMF, receive a connection setupresponse message including network slice information supported by eachAMF and network slice group information associated with a network slicegroup to which each AMF belongs in response to the connection setuprequest message, store network slice identification informationsupported by each AMF and slice group identification informationassociated with the network slice group to which each AMF belongs, andprovide network slice-related information to the UE based on the storedinformation.

The network slice-related information may include at least one of thenetwork slice identification information supported by each AMF, thenetwork slice group identification information associated with thenetwork slice group to which each AMF belongs, and networkidentification information supported by the BS.

The controller may be further configured to broadcast system informationincluding the network slice-related information.

The registration accept message may include network slice configurationinformation including updated network slice identification informationand network slice group identification information corresponding to theupdated network slice identification information.

The controller may be further configured to transmit, to the UE, aconfiguration information updating request message including updatednetwork slice identification information and network slice groupidentification information corresponding to the updated network sliceidentification information.

The requested network slice identification information may include anidentifier of at least one network slice, and the at least one networkslice may be included in the same network slice group as a network slicegroup associated with the network slice group identificationinformation.

According to another embodiment of the disclosure, a user equipment (UE)for supporting access to network slices includes: a transceiver; and acontroller configured to generate a registration request messageincluding requested network slice identification information and networkslice group identification information corresponding to the requestednetwork slice identification information based on stored network sliceconfiguration information, transmit the generated registration requestmessage to a base station (BS), receive a registration accept message inresponse to the registration request message, and transmit theregistration accept message to the UE.

The requested network slice identification information may include anidentifier of at least one network slice, and the at least one networkslice may be included in the same network slice group as a network slicegroup associated with the network slice group identificationinformation.

The registration accept message may include network slice configurationinformation including updated network slice identification informationand network slice group identification information corresponding to theupdated network slice identification information.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words and phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or,” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, such a device may be implemented in hardware, firmware orsoftware, or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.

Moreover, various functions described below can be implemented orsupported by one or more computer programs, each of which is formed fromcomputer readable program code and embodied in a computer readablemedium. The terms “application” and “program” refer to one or morecomputer programs, software components, sets of instructions,procedures, functions, objects, classes, instances, related data, or aportion thereof adapted for implementation in a suitable computerreadable program code. The phrase “computer readable program code”includes any type of computer code, including source code, object code,and executable code. The phrase “computer readable medium” includes anytype of medium capable of being accessed by a computer, such as readonly memory (ROM), random access memory (RAM), a hard disk drive, acompact disc (CD), a digital video disc (DVD), or any other type ofmemory. A “non-transitory” computer readable medium excludes wired,wireless, optical, or other communication links that transporttransitory electrical or other signals. A non-transitory computerreadable medium includes media where data can be permanently stored andmedia where data can be stored and later overwritten, such as arewritable optical disc or an erasable memory device.

Definitions for certain words and phrases are provided throughout thispatent document, those of ordinary skill in the art should understandthat in many, if not most instances, such definitions apply to prior, aswell as future uses of such defined words and phrases.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the disclosure will be more apparent from the followingdescription taken in conjunction with the accompanying drawings, inwhich:

FIG. 1 illustrates a diagram illustrating a 5G network slice structureaccording to an embodiment of the disclosure;

FIG. 2 illustrates a diagram illustrating a (radio access network(RAN)-initiated) configuration information exchange procedure between abase station (BS) and a core network entity, according to an embodimentof the disclosure;

FIG. 3 illustrates a diagram illustrating a (access management function(AMF)-initiated) configuration information exchange procedure between aBS and a core network entity, according to an embodiment of thedisclosure;

FIG. 4 illustrates a diagram illustrating a system informationtransmitting procedure of a BS, according to an embodiment of thedisclosure;

FIG. 5 illustrates a diagram illustrating types of user equipments (UEs)according to an embodiment of the disclosure;

FIG. 6 illustrates a diagram illustrating a network registrationprocedure of a UE, according to an embodiment of the disclosure;

FIG. 7 illustrates a diagram illustrating a method of updating UEconfiguration information in a registration procedure, according to anembodiment of the disclosure;

FIG. 8 illustrates a diagram illustrating a UE configuration informationupdating procedure, according to an embodiment of the disclosure;

FIG. 9 illustrates a diagram illustrating a configuration of a UE,according to an embodiment of the disclosure; and

FIG. 10 illustrates a diagram illustrating a configuration of a networkentity according to an embodiment of the disclosure.

DETAILED DESCRIPTION

FIGS. 1 through 10, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged system or device.

Hereinafter, the operation principle of the disclosure will be explainedin detail with reference to the attached drawings. While describing thedisclosure, detailed descriptions about related well known functions orconfigurations that may blur the points of the disclosure are omitted.For the same reason, some elements in the attached drawings may beexaggerated, omitted, or schematically illustrated. In addition, a sizeof each element may not totally reflect a real size of the element. Ineach drawing, the same or corresponding element is denoted by the samereference numeral.

The terms used herein are those defined in consideration of functions inthe disclosure, but the terms may vary according to the intention ofusers or operators, precedents, etc. Therefore, the terms used hereinhave to be defined based on the meaning of the terms together with thedescription throughout the specification.

The advantages and features of the disclosure and methods of achievingthem will become apparent by describing in detail embodiments of thedisclosure with reference to the accompanying drawings. The disclosuremay, however, be embodied in many different forms and should not beconstrued as limited to embodiments of the disclosure set forth herein,rather these embodiments of the disclosure are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure only defined by the claims to one of ordinaryskill in the art. In the specification, the same elements are denoted bythe same reference numerals.

It will be understood that each block of flowchart illustrations andcombinations of blocks in the flowchart illustrations may be implementedby computer program instructions. The computer program instructions maybe provided to a processor of a general-purpose computer, specialpurpose computer, or other programmable data processing apparatus, suchthat the instructions, which are executed via the processor of thecomputer or other programmable data processing apparatus, generate meansfor performing functions specified in the flowchart block or blocks. Thecomputer program instructions may also be stored in a computer sable orcomputer-readable memory that may direct the computer or otherprogrammable data processing apparatus to function in a particularmanner, such that the instructions stored in the computer usable orcomputer-readable memory produce an article of manufacture includinginstruction means that perform the functions specified in the flowchartblock or blocks. The computer program instructions may also be loadedonto the computer or other programmable data processing apparatus tocause a series of operational steps to be performed on the computer orother programmable apparatus to produce a computer implemented processsuch that the instructions that are executed on the computer or otherprogrammable apparatus provide steps for implementing the functionsspecified in the flowchart block or blocks.

In addition, each block of the flowchart illustrations may represent amodule, segment, or portion of code, which includes one or moreexecutable instructions for performing specified logical function(s). Itshould also be noted that in some alternative implementations, thefunctions noted in the blocks may occur out of the order. For example,two blocks shown in succession may in fact be executed substantiallyconcurrently or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved.

The term “˜ unit” used in the present embodiment of the disclosurerefers to a software or hardware component, such as field-programmablegate array (FPGA) or application-specific integrated circuit (ASIC),which performs certain tasks. However, the term “˜ unit” does not meanto be limited to software or hardware. A unit may be configured to be inan addressable storage medium or configured to operate one or moreprocessors. Thus, a unit may include, by way of example, components,such as software components, object-oriented software components, classcomponents, and task components, processes, functions, attributes,procedures, subroutines, segments of program code, drivers, firmware,microcode, circuitry, data, databases, data structures, tables, arrays,and variables. The functionality provided in the components and unitsmay be combined into fewer components and units or further separatedinto additional components and units. Further, the components and unitsmay be implemented to operate one or more central processing units(CPUs) in a device or a secure multimedia card.

Throughout the disclosure, the expression “at least one of a, b or c”indicates only a, only b, only c, both a and b, both a and c, both b andc, all of a, b, and c, or variations thereof.

Hereinafter, a base station (BS) is an entity that allocates resourcesto a user equipment (UE) and may be at least one of a node B, a BS, aneNode B (eNB), a gNode B (gNB), a radio access unit, a BS controller, ora node on a network. Examples of a UE may include a user equipment (UE),a mobile station (MS), a cellular phone, a smartphone, a computer, and amultimedia system capable of performing a communication function. Also,embodiments of the disclosure may be applied to other communicationsystems having a similar technical background or channel type to that ofthe embodiments of the disclosure. Also, it will be understood by one ofordinary skill in the art that embodiments of the disclosure may beapplied to other communication systems through some modificationswithout departing from the scope of the disclosure.

Hereinafter, terms indicating a connection node, terms indicatingnetwork entities, terms indicating messages, terms indicating aninterface between network entities, and terms indicating various piecesof identification information, as used in the following description, areexemplified for convenience of explanation. Accordingly, the disclosureis not limited to the terms to be described later, but other termsindicating objects having equal technical meanings may be used.

Hereinafter, for convenience of explanation, the disclosure uses termsand names defined in standards for 5G systems. However, the disclosureis not limited to the above terms and names, and may also be applied tosystems following other standards.

Although embodiments of the disclosure are described by usingcommunication systems following the 3^(rd) generation partnershipproject (3GPP) standard, it will be understood by one of ordinary skillin the art that the main essence of the disclosure may also be appliedto other communication systems having a similar technical backgroundthrough some modifications without departing from the scope of thedisclosure.

When embodiments of the disclosure are described, a slice, a service, anetwork slice, a network service, an application slice, an applicationservice, network slice information, and network slice selectionassistance information (NSSAI) may be interchangeably used.

Until now, communication systems have been designed independently ofapplications provided on the communication systems. A user firstaccesses a communication system, selects a desired application, andreceives a service. Such communication technology has been combined withtechnology such as network function virtualization (NFV) or softwaredefined networking (SDN) and has been developed into a method ofconfiguring a network slice optimized for application characteristicsfor each application in one huge network.

One network slice includes an end-to-end (E2E) logical network includinga UE to a correspondent node (e.g., a correspondent UE or acorrespondent application server). A user may access a network slicespecialized for a desired application and may receive a service. Thatis, a UE of a user may simultaneously access one or more network slices.

The 3GPP in charge of standardization of mobile communication technologyhas completed the 5G phase I standard in Rel-15, and the 5G phase Istandard includes a network slicing function. In Rel-16, a process ofdeveloping the network slicing phase II standard is being performed.

The disclosure defines, when multiple network slices are provided in a5G-based network slicing structure, structures of network slices thatmay be mutually provided and slices (i.e., mutually exclusive slices)that may not be mutually provided. Also, the disclosure defines a methodof providing UE configuration information (e.g., UE configurationinformation) of a mutually exclusive slice structure to a UE. Also, thedisclosure defines a UE registration procedure based on UE configurationinformation. Also, the disclosure defines a procedure of updating UEconfiguration information.

Also, the disclosure may provide a method of processing a control signalin a wireless communication system by receiving a first control signalfrom a network entity; processing the received first control signal; andtransmitting a second control signal generated based on the processedfirst control signal to the network entity or transmitting the secondcontrol signal generated based on the processed first control signal toanother network entity.

A mobile network operator may provide various services in a mobilecommunication network, and the services may have to satisfy respectiveservice requirements e.g., latency, communication range, data rate,bandwidth, and reliability). A mobile network operator may allocate anetwork resource suitable for a service according to each slice or eachset of specific slices. The term “network resource” used herein mayrefer to a network function (NF) or a logical resource allocation orradio resource allocation provided by the NF.

A mobile network operator may make a contract with a service providerand may configure network slices for a service provided by the serviceprovider. When a mobile network operator configures network slices,specific network slices may be mutually provided or mutually exclusivelyprovided, by a contract between the mobile network operator and aservice provider, a policy of the mobile network operator, or agovernment regulation.

FIG. 1 is a diagram illustrating a network slice structure.Single-network slice selection assistance information (S-NSSAI) definedin the 3GPP may be used as a differentiator for differentiating networkslices. Referring to FIG. 1, three network slices, that is, S-NSSAI#1160, S-NSSAI#2 165, and S-NSSAI#3 170, may be provided in a network of amobile network operator, and each S-NSSAI may refer to each networkslice. Each network slice may include network resources (e.g., NFs) usedfor providing a service supported by each network slice. The networkresources may include core network entities (e.g., an access managementfunction (AMF), a session management function (SMF), a user planefunction (UPF), and a policy control function (PCF)) and radio networkresources (e.g., a BS, a radio access network (RAN), an access network(AN), a gNB, and an eNB) defined in the 3GPP. A BS and a RAN may beinterchangeably used in the disclosure.

Referring to FIG. 1, specific network slices may share a specificnetwork resource. For example, the S-NSSAI#1 160 and the S-NSSAI#2 165may share an AMF 120, and may select SMFs 125 and 135 and UPFs 130 and140 as dedicated NFs for the S-NSSAI#1 160 and the S-NSSAI#2 165. Also,referring to FIG. 1, a specific network slice may include only dedicatedNFs for the specific network slice. For example, the S-NSSAI#3 170 mayinclude only NFs (e.g., an AMF 145, an SMF 150, and a UPF 155) belongingto the S-NSSAI#3 170 without an NF shared with other network slices.

Referring to FIG. 1, network slices that may share a specific networkresource may be differentiated as one slice group. For example, theS-NSSAI#1 160 and S-NSSAI#2 165 that share the AMF 120 may be referredto as a slice group 1 175, The S-NSSAI#3 170 that does not share aresource with other network slices may be referred to as a slice group 2180 that is another slice group.

In each AMF according to an embodiment of the disclosure, sliceinformation (e.g., S-NSSAI) that may be provided by the AMF and slicegroup information slice group ID) associated with a slice group to whichthe AMF belongs may be set and stored. For example, the AMF 120 maystore information indicating that slices that may be provided by the AMF120 are the S-NSSAI#1 160 and the S-NSSAI#2 165 and a slice group towhich the AMF 145 belongs is the slice group 1 175,

Also, referring to FIG. 1, a RAN may be shared by multiple networkslices. For example, a BS 115 may be connected to both the AMF 120supporting the S-NSSAI#1 160 and the S-NSSAI#2 165 and the AMF 145supporting the S-NSSAI#3 170.

FIGS. 2 and 3 are diagrams illustrating a configuration informationexchange procedure between a BS and a core network entity (e.g., an AMF)to provide network slices.

Referring to FIG. 2, a BS 210 may transmit a connection setup requestmessage 220 to an AMF 215 that is a core nets network entity. Networkslice information supported by the BS 210 may be included in theconnection setup request message 220. The network slice information mayinclude a list of one or more S-NSSAIs.

According to an embodiment of the disclosure, the AMF 215 receiving theconnection setup request message 220 may store, in the AMF 215, thenetwork slice information supported by the BS 210 included in theconnection setup request message 220 in operation 225.

According to an embodiment of the disclosure, the AMF 215 receiving theconnection setup request message 220 may transmit a connection setupresponse message 230 as a reply to the BS 210. Network slice information(e.g., S-NSSAI) supported by the AMF 215 and slice group information(slice group ID) associated with a slice group to which the AMF 215belongs based on configuration information stored in the AMF 215described with reference to FIG. 1 may be included in the connectionsetup response message 230.

According to an embodiment of the disclosure, the network sliceinformation and the slice group information included in the connectionsetup response message 230 may follow the following format.

{SG ID, a list of supported S-NSSAIs}

For example, {SG ID 1, (S-NSSAT#1, S-NSSAT#2)} may be included in aconnection setup response message transmitted by the AMF 120 of FIG. 1.

Also, according to an embodiment of the disclosure, the network sliceinformation and the slice group information included in the connectionsetup response message 230 may follow the following format.

{a list of SG ID and supported S-NSSAI}

For example, {SG ID 1, S-NSSAI#1), (SG ID 1, S-NSSAI#2)} may be includedin the connection setup response message transmitted by the AMF 120 ofFIG. 1.

The BS 210 receiving the connection setup response message 230 maystore, in the BS 210, the network slice information supported by the AMF215 and the slice group information included in the connection setupresponse message 230 in operation 235. Information stored in the BS 210may be used in order for the BS 210 receiving a response request messagefrom a UE to select an AMF to which a corresponding message is to betransmitted.

Referring to FIG. 3, an AMF 315 that is a core network entity maytransmit a connection setup request message 320 to a BS 310. Networkslice information (e.g., S-NSSAI) supported by the AMF 315 and slicegroup information (e.g., slice group ID) associated with a slice groupto which the AMF 315 belongs based on configuration information storedin the AMF 315 described with reference to FIG. 1 may be included in theconnection setup request message 320.

According to an embodiment of the disclosure, the network sliceinformation and the slice group information included in the connectionsetup request message 320 may follow the following format.

{SG ID, a list of supported S-NSSAIs}

For example. {SG ID 1, (S-NSSAT#1, S-NSSAT#2)} may be included in aconnection setup response message transmitted by the AMF 120 of FIG. 1.

Also, according to an embodiment of the disclosure, the network sliceinformation and the slice group information included in the connectionsetup request message 320 may follow the following format.

{a list of SG ID and supported S-NSSAI}

For example, {(SG ID 1, S-NSSAI#1), (SG ID 1, S-NSSAI#2)} may beincluded in the connection setup response message transmitted by the AMF120 of FIG. 1.

The BS 310 receiving the connection setup request message 320 may store,in the BS 310, the network slice information supported by the AMF 315and the slice group information included in the connection setup requestmessage 320 in operation 325. Information stored in the BS 310 may beused in order for the BS 310 receiving a response request message from aUE to select an AMF to which a corresponding message is to betransmitted.

The BS 310 receiving the connection setup request message 320 maytransmit a connection setup response message 330 to the AMF 315. Networkslice information supported by the BS 310 may be included in theconnection setup response message 330. The network slice information mayinclude a list of one or more S-NSSAIs.

The AMF 315 receiving the connection setup response message 330 maystore, in the AMF 315, the network slice information supported by the BS310 included in the connection setup response message 330 in operation335.

An AMF according to an embodiment of the disclosure may perform aprocedure of FIG. 2 or 3. The AMF may store network slice informationsupported by each BS.

Also, a BS according to an embodiment of the disclosure may perform aprocedure of FIG. 2 or 3 with one or more AMFs. The BS may store networkslice information supported by each AMF and slice group information.

FIG. 4 is a diagram illustrating a procedure in which a BS notifiesnetwork slice information to a UE according to an embodiment of thedisclosure. Referring to FIG. 4, the BS 415 may transmit a systeminformation message 420 to a UE 410. The system information message 420may be transmitted by using a broadcast communication method and may bereceived by UEs around the BS 415.

According to an embodiment of the disclosure, network slice-relatedinformation that may be provided by the BS 415 may be included in thesystem information message 420. The network slice-related informationmay be configured based on network slice information supported by eachAMF connected to the BS 415 and slice group information and networkslice information supported by the BS 415 collected by using theprocedure of FIG. 2 or 3.

The UE 410 receiving the system information message 420 may determinewhich BS is to be accessed based on the network slice-relatedinformation included in the system information message 420. For example,when one or more BSs are located around a UE, the UE 410 may receivesystem information messages from a plurality of BSs. The BSs may supportdifferent network slices. Different network slice information may beincluded in the system information messages 420 received from the BSs.The UE 410 receiving the system information messages from the pluralityof BSs may determine which BS is to be accessed based on the networkslice-related information supported by each BS included in the receivedmessages.

FIG. 5 is a diagram illustrating types of UEs according to an embodimentof the disclosure. A UE 510 supporting network slices defined in the3GPP may be divided into a UE 515 that is a Release 15 UE supporting aRelease 15 network slice function and a UE 520 that is a UE afterRelease 16 and supports both the Release 15 network slice function and afunction added after the Release 16.

Referring to FIG. 5, the UE 515 according to an embodiment of thedisclosure may be identified or recognized as a UE 525 that may notsupport a mutually exclusive access to network slices function that isadded in the Release 16.

Also, referring to FIG. 5, the UE 520 after the Release 16 according toan embodiment of the disclosure may be divided into a UE 535 thatsupports the mutually exclusive access to network slices function thatis added in the Release 16 and a UE 530 that may not support themutually exclusive access to network slices function.

Each of the UEs 525, 530, and 535 according to an embodiment of thedisclosure may store, in the UE, network slice-related configurationinformation in order of use network slices provided by a mobile networkoperator, The network slice-related configuration information may bereferred to as configured NSSAI defined in the 3GPP.

The network slice-related configuration information stored in the UEaccording to an embodiment of the disclosure may follow the followingformat of Table 1.

TABLE 1 {SG ID, a list of subscribed S-NSSAIs} SG ID S-NSSAIs SG ID Alist of S-NSSAIs SG ID A list of S-NSSAIs . . . . . .

For example, when a UE 110 of FIG. 1 may use three network slicesS-NSSAI#1, S-NSSAI#2, and S-NSSAI#3, configuration information of the UE110 may be represented as shown in Table 2.

TABLE 2 SG ID S-NSSAIs SG ID 1 S-NSSAI#1, S-NSSAI#2 SG ID 2 S-NSSAI#3

According to an embodiment of the disclosure, when UE configurationinformation is stored in the UE 535 supporting the mutually exclusiveaccess to network slices function, the UE 535 may interpret (identify orrecognize) both SG ID information and S-NSSAIs information.

According to an embodiment of the disclosure, when UE configurationinformation is stored in the UEs 525 and 530 that do not support themutually exclusive access to network slices function, the UEs 525 and530 may ignore the SG ID information and may interpret (identify orrecognize) only the S-NSSAIs information.

Alternatively, the network slice-related configuration informationstored in the UE according to an embodiment of the disclosure may followthe following format of Table 3.

TABLE 3 {a list of SG ID and subscribed S-NSSAI} SG ID S-NSSAI SG IDS-NSSAI SG ID S-NSSAI . . . . . .

For example, when the UE 110 of FIG. 1 may use the three network slicesS-NSSAI#1, S-NSSAI#2, and S-NSSAI#3, configuration information of the UEmay be represented as shown in Table 4.

TABLE 4 SG ID S-NSSAI SG ID 1 S-NSSAI#1 SG ID 1 S-NSSAI#2 SG ID 2S-NSSAI#3

According to an embodiment of the disclosure, when UE configurationinformation is stored in the UE 535 supporting the mutually exclusiveaccess to network slices function, the UE 535 may interpret both SG IDinformation and S-NSSAI information.

According to an embodiment of the disclosure, when UE configurationinformation is stored in the UEs 525 and 530 that do not support themutually exclusive access to network slices function, the UEs 525 and530 may ignore the SG ID information and may interpret only the S-NSSAIinformation.

FIG. 6 is a diagram illustrating a network registration procedure of aUE according to an embodiment of the disclosure.

A UE 610 according to an embodiment of the disclosure may generate arequested NSSAI 635 based on network slice configuration informationstored in the LJE 610. The requested. NSSAI 635 may include one or moreS-NSSAIs. The UE 610 according to an embodiment of the disclosure maygenerate (or configure) the requested NSSAI 635 by using only S-NSSAIsbelonging to the same slice group. For example, the UE 610 may seestored network slice configuration information, may select SASSAI#1 andS-NSSAI#2 belonging to SG 1 that is the same slice group, and maygenerate the requested NSSAI 635. Also, the UE 610 may see the storednetwork slice configuration information, and may determine thatS-NSSAI#3 belongs to SG ID 2 and thus may not be included in therequested NSSAI 635.

The UE 610 according to an embodiment of the disclosure may access anetwork and may transmit a registration request message 640 in order touse a mobile communication service. In this case, the UE 610 may causethe requested NSSAI 635 generated by the UE 610 to be included in theregistration request message 640. Also, the UE 610 may cause a slicegroup ID to which S-NSSAIs included in the requested NSSAI 635 generatedby the UE 610 belong to be included in the registration request message640. For example, the S-NSSAI#1 and the S-NSSAI#2 and the SG ID 1 thatis a slice group ID to which the S-NSSAIs belong may be included asrequested NSSAIs requested by the UE 610 in the registration requestmessage 640.

Also, according to an embodiment of the disclosure, the UE 610 may causethe requested NSSAI 635 generated by the UE 610 and the slice group IDto be included in a radio resource control (RRC) message and to betransmitted to a BS 615.

The BS 615 receiving the registration request message 640 may determineto which AMF the registration request message 640 is to be transmittedbased on the requested NSSAI 635 and the slice group ID received fromthe UE 610 and slice information supported by an AMF obtained throughthe procedure of FIG. 2 or 3 in operation 645.

When the BS 615 according to an embodiment of the disclosure determinesto which AMF the registration request message 640 is to be transmitted,the BS 615 may check whether there is an AMF supporting all requestedNSSAIs included in the registration request message 640 transmitted bythe UE 610. When there is an AMF supporting all of the requested NSSAIsrequested by the UE 610, the BS 615 may transmit a registration requestmessage 650 of the UE 610 to the AMF.

When the BS 615 according to an embodiment of the disclosure determinesto which AMF the registration request message 640 is to be transmitted,the BS 615 may check whether there is an AMF supporting all requestedNSSAIs included in the registration request message 640 transmitted bythe UE 610. When there is no AMF supporting all of the requested NSSAIsrequested by the UE 610, the BS 615 may check whether there is an AMFsupporting slice group ID requested by the LIE 610 included in theregistration request message 640 transmitted by the UE 610. When thereis an AMF 620 supporting the slice group ID requested by the UE 610, theBS 615 may transmit the registration request message 650 of the UE 610to the AMF 620.

When the BS 615 according to an embodiment of the disclosure determinesto which AMF the registration request message 640 is to be transmitted,the BS 615 may check whether there is an AMF supporting all requestedNSSAIs included in the registration request message 640 transmitted bythe UE 610. When there is no AMF supporting all of the requested NSSAIsrequested by the UE 610, the BS 615 may check whether there is an ANFsupporting slice group ID requested by the UE 610 included in theregistration request message 640 transmitted by the UE 610. When thereis no AMF supporting the slice group ID requested by the UE 610, the BS615 may transmit the registration request message 650 of the UE 610 to adefault AMF based on pre-set information.

The AMF 620 receiving the registration request message 650 of the UE 610may request a user data management (UDM) for subscription information ofthe UE 610, and may obtain the subscription information of the UE, 610from the UDM. Network slice information to which the UE 610 subscribesmay be included in the subscription information of the UE 610. S-NSSAIinformation and slice group ID information which may be used by the UE610 may be included in the network slice information to which the UE 610subscribes. The AMF 620 may check whether there is appropriatesubscription information that may use slices (requested NSSAIs)requested by the UE 610 based on the subscription information of the UE610 obtained from the UDM in a subscription information checkingprocedure 655.

After the AMF 620 according to an embodiment of the disclosure checksservice use authentication of the 610 through the subscriptioninformation checking procedure 655 of the UE 610, the AMF 620 maydetermine whether the AMF 620 may support the requested NSSAIs requestedby the UE 610. For example, when the S-NSSAI#1 and the S-NSSAI#2 areincluded in the requested NSSAIs requested by the UE 610 and the AMF 620may support both the S-NSSAI#1 and the S-NSSAI#2, an AMF reallocationprocedure 660 of FIG. 6 may be omitted. Alternatively, for example, whenthe S-NSSAI#1 and the S-NSSAI112 are included in the requested NSSAIsrequested by the UE 610 and the AMF 620 may not support one or moreS-NSSAIs from among network slices requested by the UE 610, the AMFreallocation procedure 660 of FIG. 6 may be performed.

When the AMF 620 may not support one or more S-NSSAIs from among thenetwork slices requested by the UE 610, the AMF 620 may perform the AMFreallocation procedure 660. The AMF 620 may transmit an AMF reallocationrequest message to a network slice selection function (NSSF) 625. Therequested NSSAIs requested by the UE 610 and the slice group ID may beincluded in the AMF reallocation request message.

The NSSF 625 receiving the AMF reallocation request message may checkAMF information that may support the requested NSSAIs requested by theUE 610. The NSSF 625 may check an AMF belonging to the same slice groupas a slice group requested by the UE 610 from among AMFs that maysupport the requested NSSAIs requested by the UE 610. The NSSF 625 maycause AMF information belonging to the same slice group as a slice grouprequested by the UE 610 from among AMFs that may support the requestedNSSAIs requested by the UE 610 to be included in the AMF reallocationresponse message and to be transmitted to the AMF 620.

After completing the subscription information checking procedure 655 ofthe UE 610 and the AMF reallocation procedure 660, the AMF 620 accordingto an embodiment of the disclosure may finally determine network slices(allowed NSSAIs) that may be used by the UE 610. The AMF 620 maytransmit registration accept messages 665 and 670 to the UE 610. Theallowed NSSAIs that are network slice information available to the UE610 may be included in the registration accept messages 665 and 670.

FIG. 7 is a diagram illustrating a procedure of updating network sliceconfiguration information of a UE according to an embodiment of thedisclosure. A UE 710 transmits a registration request message 740 to anAMF 720 to access a network, Step 1 using the registration requestmessage 740 of FIG. 7 schematically illustrates Step 1 using therequested NSSAI 635 through Step 4 using the registration requestmessage 650 of FIG. 6. The UE 710 according to an embodiment of thedisclosure may configure a requested NSSAI by using one or more S-NSSAIsbelonging to the same slice group based on configuration information ofthe UE 710, and may cause slice group ID information of the slice groupto be included and to be transmitted to the AM 720F.

The AMF 720 receiving the registration request message 740 mayinvestigate validity of the requested NSSAI requested by the UE 710 andthe slice group ID information. That is, the AMF 720 may check whetherthe S-NSSAIs included in the requested NSSAI and the slice group arecorrectly mapped. For example, the AMF 720 manages S-NSSAI#1 andS-NSSAI#2 as SG ID 1 and S-NSSAI#3 as SG ID 2 in the network, and whenthe S-NSSAI#1 and the S-NSSAI#3 are included in the requested NSSAI sentby the UE 710 and the Si ID 1 is included in the slice group IDinformation, the AMF 720 may determine that the UE 710 has incorrectconfiguration information. When the UE 710 has incorrect configurationinformation, the AMF 720 may update the configuration information of theUE 710 by providing recent configured NSSAI to the UE 710.

The AMF 720 according to an embodiment of the disclosure may transmit aregistration accept message 750 as a reply during a UE registrationprocedure. The configured NSSAI may be included in the registrationaccept message 750. Also, are allowed NSSAI which may be used by the LT710 by accessing the network may also be included in the registrationaccept message 750.

The UE 710 receiving the registration accept message 750 may replaceconfigured NSSAI that is network configuration information stored in theUE 710 with the received configured NSSAI.

FIG. 8 is a diagram illustrating a procedure of updating network sliceconfiguration information of a UE according to an embodiment of thedisclosure. According to an embodiment of the disclosure of FIG. 8, anetwork may start a configuration information updating procedure of a UE810 due to a mobile network operator policy, a network deploymentchange, and a temporary network failure. The network may determine arecent configured NSSAI to be transmitted to the UE 810. The network maytransmit a configuration information updating request message 845including the recent configured NSSAI to the UE 810. The UE 810receiving the configuration information updating request message 845 mayreplace configured NSSAI that is network configuration informationstored in the UE 810 with the received configured NSSAI.

According to embodiments of the disclosure, a mobile network operatormay efficiently manage and provide mutually exclusive network slices.

FIG. 9 is a diagram illustrating a configuration of a UE according to anembodiment of the disclosure.

A UE according to an embodiment of the disclosure may include aprocessor 910 that controls an overall operation of the UE, atransceiver 920 that includes a transmitter and a receiver, and a memory930. The disclosure is not limited thereto, and the UE may includeelements more or fewer than those illustrated in FIG. 9.

According to an embodiment of the disclosure, the transceiver 920 maytransmit/receive a signal to/from other network entities. The signaltransmitted/received to/from other network entities may include controlinformation and data. Also, the transceiver 920 may receive a signalthrough a wireless channel and may output a signal to the processor 910,and may transmit a signal output from the processor 910 through thewireless channel.

According to an embodiment of the disclosure, the processor 910 maycontrol the UE to perform one of the above embodiments of thedisclosure. The processor 910 and the transceiver 920 are notnecessarily implemented as modules, and may be implemented as oneelement such as a single chip. The processor 910 and the transceiver 920may be electrically connected. Also, the processor 910 may be a circuit,an application-specific circuit, or at least one processor.

According to an embodiment of the disclosure, the memory 930 may store abasic program for operating the UE, an application program, and datasuch as configuration information. In particular, the memory 930provides stored data according to a request of the processor 910. Thememory 930 may include a storage medium such as a read-only memory(ROM), a random-access memory (RAM), a hard disc, a compact disc(CD)-ROM, or a digital versatile disc (DVD), or a combination thereof.Also, a plurality of the memories 930 may be provided. Also, theprocessor 910 may perform embodiments of the disclosure based on aprogram for performing the embodiments of the disclosure stored in thememory 930.

FIG. 10 is a diagram illustrating a configuration of a network entityaccording to an embodiment of the disclosure.

A network entity according to an embodiment of the disclosure mayinclude a processor 1010 that controls an overall operation of thenetwork entity, a transceiver 1020 that includes a transmitter and areceiver, and a memory 1030. The disclosure is not limited thereto, andthe network entity may include elements more or fewer than thoseillustrated in FIG. 10.

According to an embodiment of the disclosure, the transceiver 1020 maytransmit/receive a signal to/from at least one of other network entitiesor a UE. The signal transmitted/received to/from at least one of theother network entities or the UE may include control information anddata.

According to an embodiment of the disclosure, the processor 1010 maycontrol the network entity to perform one of the above embodiments ofthe disclosure. The processor 1010 and the transceiver 1020 are notnecessarily implemented as separate modules and may be implemented asone element such as a single chip. The processor 1010 and thetransceiver 1020 may be electrically connected. Also, the processor 1010may be a circuit, an application-specific circuit, or at least oneprocessor.

According to an embodiment of the disclosure, the memory 1030 may storea basic program for operating the network entity, an applicationprogram, and data such as configuration information. In particular, thememory 1030 provides stored data according to a request of the processor1010. The memory 1030 may include a storage medium such as a ROM, a RAM,a hard disc, a CD-ROM, or a DVD, or a combination thereof. Also, aplurality of the memories 1030 may be provided. Also, the processor 1010may perform embodiments of the disclosure based on a program forperforming the embodiments of the disclosure stored in the memory 1030.

It will be understood that a diagram illustrating a configuration, adiagram illustrating a method of transmitting a control/data signal, adiagram illustrating an operation procedure, and a diagram illustratingconfigurations in the above are not intended to limit the scope of thedisclosure. That is, all of elements, entities, or steps of operationsdescribed in embodiments of the disclosure should not be construed asessential elements for carrying out the disclosure, and the disclosuremay be carried out only with some elements without departing from thescope of the disclosure. Also, the embodiments of the disclosure may beperformed in combination as needed. For example, some of methodsprovided by the disclosure may be combined to operate a network entityand a UE.

Operations of a BS or a UE in the above may be performed by providing amemory device storing corresponding program code in an element of the BSor the UE. That is, a controller of the BS or the UE may perform theoperations by reading and executing the program code stored in thememory device by means of a processor or a central processing unit(CPU).

As described herein, various components or modules in an entity, a BS,or a UE in the above may operate by using a hardware circuit, e.g., acomplimentary metal oxide semiconductor-based logic circuit, firmware,software, and/or a hardware circuit such as a combination of hardwarefirmware, and/or software embedded in a machine-readable medium. Forexample, various electrical structures and methods may be carried out byusing electrical circuits such as transistors, logic gates, and ACISs.

When a method is implemented by software, a computer-readable storagemedium for storing one or more programs (software modules) may beprovided. The one or more programs stored in the computer-readablestorage medium are configured to be executed by one or more processorsin an electronic device. The one or more programs include instructionsfor allowing the electronic device to perform methods according to theclaims of the disclosure or embodiments of the disclosure described inthe specification of the disclosure.

Such programs (software modules and software) may be stored in a RAM, anon-volatile memory including a flash memory, a ROM, an electricallyerasable programmable read-only memory (EEPROM), a magnetic disc storagedevice, a CD-ROM, a DVD, another optical storage device, or a magneticcassette. Alternatively, the programs may be stored in a memoryconfigured by combining some or all of them. Also, the configured memorymay include a plurality of memories.

Also, the programs may be stored in an attachable storage deviceaccessible through a communication network such as the Internet, anintranet, a local area network (LAN), a wide LAN (WLAN), or a storagearea network (SAN), or a combination thereof. This storage device mayaccess a device for performing embodiments of the disclosure through anexternal port. Also, a separate storage device on a communicationnetwork may access a device for performing embodiments of thedisclosure.

The disclosure provides an apparatus and method of effectively providingservices in a mobile communication system.

In specific embodiments of the disclosure described above, componentsincluded in the disclosure were expressed singular or plural inaccordance with the specific embodiments of the disclosure. However,singular or plural representations are selected appropriately for thesake of convenience of explanation, the disclosure is not limited tosingular or plural constituent elements, and even expressed as asingular element, it may be composed of plural elements, and vice versa.

While the particular embodiments of the disclosure have beenparticularly described, it will be understood by one of ordinary skillin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the disclosure. Hence,the scope of the disclosure is not defined by the embodiments of thedisclosure but by the claims and all modifications or alternativesderived from the scope and spirit of the claims and equivalents thereoffall within the scope of the disclosure. That is, it will be obvious toone of ordinary skill in the art that various modifications may be madebased on the technical scope of the disclosure. Also, two or more of theembodiments of the disclosure may be combined. For example, some ofmethods provided by the disclosure may be combined with each other tooperate a BS and a UE. Also, although the embodiments of the disclosureare described based on 5G and new radio (NR) systems, modificationsbased on the technical scope of the embodiments of the disclosure may beapplied to other communication systems such as long term evolution(LTE), long term evolution advanced (LTE-A), and LTE-A-Pro systems.

While the disclosure has been particularly shown and described withreference to embodiments thereof, it will be understood by one ofordinary skill in the art that various changes in form and details maybe made therein without departing from the spirit and scope of thedisclosure as defined by the following claims. Hence, the scope of thedisclosure is not defined by the embodiments of the disclosure but bythe claims and all modifications or alternatives derived from the scopeand spirit of the claims and equivalents thereof fall within the scopeof the disclosure.

Although the present disclosure has been described with variousembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present disclosure encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method, performed by a base station (BS), ofsupporting access to network slices in a wireless communication system,the method comprising: receiving a connection setup request messagecomprising network slice identification information supported by the BS,from at least one access and mobility management function (AMF): andtransmitting a connection setup response message comprising networkslice information supported by each AMF and network slice groupidentification information associated with a network slice group towhich each AMF belongs, in response to the connection setup requestmessage, and wherein the network slice identification informationsupported by each AMF and the network slice group identificationinformation associated with the network slice group to which each AMFbelongs is stored by the AMF.
 2. The method of claim 1, furthercomprising: receiving a registration request message comprisingrequested network slice identification information of a user equipment(UE) and the network slice group identification informationcorresponding to the requested network slice identification information;selecting an AMF to which the registration request message is to betransmitted, based on the registration request message, the nets networkslice group identification information corresponding to the requestednetwork slice identification information, and network slice informationsupported by the at least one AMF stored in the BS; transmitting theregistration request message to the AMF; receiving a registration acceptmessage in response to the registration request message; andtransmitting the registration accept message to the UE.
 3. The method ofclaim 2, further comprising: providing network slice-related informationto the UE, based on the stored network slice identification informationand the stored network slice group identification information.
 4. Themethod of claim 3, wherein the network slice-related informationcomprises at least one of the network slice identification informationsupported by each AMF, the network slice group identificationinformation associated with the network slice group to which each AMFbelongs, or the network slice identification information supported bythe BS.
 5. The method of claim 4, wherein the providing of the networkslice-related information to the UE comprises broadcasting systeminformation comprising the network slice-related information.
 6. Themethod of claim 2, wherein the registration accept message comprisesnetwork slice configuration information comprising updated network sliceidentification information and the network slice group identificationinformation corresponding to the updated network slice identificationinformation.
 7. The method of claim 2, further comprising transmitting,to the UE, a configuration information updating request messagecomprising network slice configuration information comprising updatednetwork slice identification information and the network slice groupidentification information corresponding to the updated network sliceidentification information.
 8. The method of claim 2, wherein therequested network slice identification information comprises anidentifier of at least one network slice, and the at least one networkslice is included in a same network slice group as a network slice groupassociated with the network slice group identification information.
 9. Amethod, performed by a user equipment (UE), of supporting access tonetwork slices in a wireless communication system, the methodcomprising: generating a registration request message comprisingrequested network slice identification information and network slicegroup identification information corresponding to the requested networkslice identification information, based on stored network sliceconfiguration information; transmitting the generated registrationrequest message to a base station (BS); receiving a registration acceptmessage in response to the registration request message; andtransmitting the registration accept message to the BS, wherein theregistration accept message comprises network slice configurationinformation including updated network slice identification informationand the network slice group identification information corresponding tothe updated network slice identification information.
 10. The method ofclaim 9, wherein the requested network slice identification informationcomprises an identifier of at least one network slice, and the at leastone network slice is included in a same network slice group as a networkslice group associated with the network slice group identificationinformation.
 11. A base station (BS) for supporting access to networkslices, the BS comprising: a transceiver; and a controller coupled tothe transceiver and configured to: receive a connection setup requestmessage comprising network slice identification information supported bythe BS, from at least one access and mobility management function (AMF);and transmit a connection setup response message comprising networkslice information supported by each AMF and network slice groupidentification information associated with a network slice group towhich each AMT belongs, in response to the connection setup requestmessage, and wherein the network slice identification informationsupported by each AMF and the network slice group identificationinformation associated with the network slice group to which each AMFbelongs is stored by the AMF.
 12. The BS of claim 11, wherein thecontroller is further configured to: receive a registration requestmessage comprising requested network slice identification information ofa user equipment (UE) and the network slice group identificationinformation corresponding to the requested network slice identificationinformation, select an AMF to which the registration request message isto be transmitted, based on the registration request message, thenetwork slice group identification information corresponding to therequested network slice identification information, and network sliceinformation supported by the at least one AMF stored in the BS, transmitthe registration request message to the AMF, receive a registrationaccept message in response to the registration request message, andtransmit the registration accept message to the UE.
 13. The BS of claim12, wherein the controller is further configured to: provide networkslice-related information to the UE based on the stored network slicegroup identification information.
 14. The BS of claim 13, wherein thenetwork slice-related information comprises at least one of the networkslice identification information supported by each AMF, the networkslice group identification information to which each AMF belongs, or thenetwork slice identification information supported by the BS.
 15. The BSof claim 14, wherein the controller is further configured to broadcastsystem information comprising the network slice-related information. 16.The BS of claim 12, wherein the registration accept message comprisesnetwork slice configuration information comprising updated network sliceidentification information and the network slice group identificationinformation corresponding to the updated network slice identificationinformation.
 17. The BS of claim 12, wherein the controller is furtherconfigured to transmit, to the UE, a configuration information updatingrequest message comprising updated network slice identificationinformation and the network slice group identification informationcorresponding to the updated network slice identification information.18. The BS of claim 12, wherein the requested network sliceidentification information comprises an identifier of at least onenetwork slice, and the at least one network slice is included in a samenetwork slice group.
 19. A user equipment (UE) for supporting access tonetwork slices, the UE comprising: a transceiver; and a controllerconfigured to: generate a registration request message comprisingrequested network slice identification information and network slicegroup identification information corresponding to the requested networkslice identification information based on stored network sliceconfiguration information; transmit the generated registration requestmessage to a base station (BS); receive a registration accept message inresponse to the registration request message; and transmit theregistration accept message to the BS, wherein the registration acceptmessage comprises network slice configuration information comprisingupdated network slice identification information and the network slicegroup identification information corresponding to the updated networkslice identification information.
 20. The UE of claim 19, wherein therequested network slice identification information comprises anidentifier of at least one network slice, and the at least one networkslice is included in a same network slice group.